The 640 MEG Shareware Studio 2

home *** CD-ROM | disk | FTP | other *** search

/ The 640 MEG Shareware Studio 2 / The 640 Meg Shareware Studio CD-ROM Volume II (Data Express)(1993).ISO / dbase / bibl76.zip / BIBL.DOC next >

Wrap

Text File | 1992-09-23 | 57KB | 1,365 lines

BIBL release 7.6 (c) 1991,92 GMUtant Software Clyde W. Grotophorst Route 1, Box 296 Hamilton, Virginia 22068 U.S.A. This documentation covers both the SHAREWARE and REGISTERED versions of the package. Non-registered users of this software are granted a limited license to make an evaluation copy for trial use on a private, non-commercial basis, for the express purpose of determining whether BIBL meets their needs. At the end of this trial period, (30 days) you should either register your copy or discontinue use. Registration licenses you to use the product on a regular basis. Registration also provides you with access to the GMUtant Online BBS ((703) 993-2219) as a registered user--where you may receive support, leave questions, requests for enhancements, or download the latest release of the program. The registered version offers expanded capabilities. Registering BIBL will also allow you to download special programs from the GMUtant OnLine BBS--for example, BIBL286 is a version of BIBL using machine code for the 80286 or 80386 processor. This allows BIBL to take better advantage of these CPUs and creates a slightly smaller BIBL.EXE file. Registration requires a contribution of $ 39.00 to the author, as a reimbursement for the time spent working on this program. Once you have registered, you will be given a registration number. You may 'upgrade' your SHAREWARE version to REGISTERED by entering that number into BIBL (via CONVERT on the maintenance menu). By using this method, you may instantly upgrade any subsequent release without having to call our BBS to download the file. If you have registered a previous version of BIBL, you are also a registered user of any subsequent version. You may upgrade at any time by sending $ 5.00 to the address below. The latest version will be sent by return 1st Class mail (specify disk size). Send your name, address and registration payment to: Clyde W. Grotophorst Route 1, Box 296 Hamilton, Virginia 22068 ** CREDIT CARD ORDERS ** You may also order the registered version of BIBL from Public (software) Library with your MasterCard, Visa, American Express, or Discover Card by calling 800-2424-PSL or 713-524-6394 or by FAX to 713-524-6398, or by CompuServe to 71355,470 or by mail to PsL, P.O. Box 35705, Houston, Texas 77235-5705. These numbers are for ordering only. The cost is $ 39.00 which includes a copy of the latest registered version to you by return 1st class mail. We've included sample records with BIBL for demonstration purposes. The sample database and index are inside BIBLDEMO.EXE. Type BIBLDEMO at the DOS prompt to extract these files. You may delete DEMO.DAT and DEMO.IX when you are ready to begin entering information you want to keep. To see the sorts of things included in the sample file, and to study how you might use the fields in a BIBL record, activate BIBL then press L, the last record in the file will display. Press [B] to move backward through the file. Q U I C K S T A R T Copy BIBL.EXE to a sub-directory on your disk (e.g., C:\BIBL) then type BIBL to activate the program. If you have not extracted the demo database, enter the name of the database you want to create. If you want to use the sample database instead of beginning with an empty one, type BIBLDEMO before running BIBL. This will extract the demonstration files (DEMO.DAT and DEMO.IX). Minimum files needed: BIBL.EXE and BIBL.HLP BIBL Features [SHAREWARE and REGISTERED]: - an unlimited number of databases are supported. - move records from one database to another - menu-driven. - mouse-support for most areas of the program. - easily understood user interface - five indexes are maintained (in a single file) for fast retrieval and sorted extracts (author, author/title, title, subject, and keyword) - up to 9 words from the keyword field are indexed individually. - produces bibliographies in several forms (brief, annotated, full (and with registered version, labelled) based on information in any field. Each bibliography is sorted by author, then within author, by title. Registered version also supports searching *anywhere* in a record for matches. - user-selected fields for output (soft return option available). - when no match is made on an indexed search, BIBL displays where in the index your query would have appeared (near misses). - produces a wide variety of lists (in ASCII form) which may be printed or edited with any word processor that accepts ASCII files for input. - use WordPerfect or other large program as your external editor/viewer/printing program. BIBL's memory management routines to enable even WordPerfect to run as a 'child' process. - if desired, BIBL will run in a 'read-only' mode. This allows copies of your database to be accessed by the public but protects against editing, deleting or otherwise modifying the file. - BIBL offers an ASCII file viewer that supports a mouse, and is moveable, resizeable, and ZOOMable. - Index progress graph displays during reindexing. - ability to print or save to disk any record. - main menu screen always reports active database and number of records in that file. - verification of subject and keywords during data entry (if desired) - BIBL shells out to PKZIP, LHA or ARJ to create compressed backup copies of your database. BIBL will find the compression utility if it exists ANYWHERE on your DOS path. - Boolean AND, OR, NOT searching supported for ALL fields. Up to four terms may be used. May also limit search to descriptor field. - Selected reports (list of subjects, list of titles, etc) may be viewed onscreen and/or sent to disk. - BIBL can export a comma-delimited verison of data - any ASCII file may be used for display when I (INFORMATION) is pressed on the main menu. - Shell to DOS with heap compression. - Use an external program as your file viewer (editor/printer) REGISTERED version adds these features: BIBL will store index data in EMS (Expanded Memory) if it is available on your system...otherwise, a 40% of available RAM (after BIBL loads) is devoted to in-memory index storage. BIBL will allocate up to 33% of available EMS to index storage. EMS speeds retrieval and cut reindexing time for larger databases. In tests on systems without disk caching, we found an average improvement of 33%. Using the "LABELLED" output option under BIBLIOGRAPHIES, you may create an ASCII (*. BIX) file of records suitable for import to other databases via the ASCII Import option on the Maintenance menu. Using this method you also have the option of deleting exported records from your original file as they transfer. Bibliographies (option D under EXPORT) as well as other reports may be created in 'word-processing' form (this will put soft returns in your file within a given citation, hard returns between them). This makes it much easier to edit the file with a word processor. Rename Author, Title, Publisher, Location and Subject fields to any name you choose for individual databases. BIBL will refer to these new field names throughout the program. You may also change ANY field's label on the display, add and/or edit screens. Bibliographies. Registered version supports export of records based on ANY field in the record, not just Author, Publisher, Subject, or Descriptor. Even *anywhere* in the record. When running a BOOLEAN search, you may send matching records to disk if desired. BIBL offers two formats for output (BIX or unlabelled). Selecting BIX format enables you to move the matching data to another BIBL database. Store Datafiles and Indexes (*.DAT and *.IX) on another drive or in another subdirectory. This enables you to use BIBL on remote disks if desired (e.g., on a LAN). Global Find & Replace for text in ANY field, across the database. BIBL will run in 43/50 line mode. Great when using DESQview. I N S T A L L A T I O N Copy BIBL.EXE and BIBL.DOC to a sub─directory. If you want to experiment with the sample database we provide, copy BIBLDEMO.EXE to this sub-directory as well. Type BIBLDEMO at the DOS prompt to extract the demostration files, then type BIBL to activate the program. After you have experimented with the capabilities of BIBL using the demo database, delete DEMO.DAT and the DEMO.IX file. When you next activate BIBL, you will have the opportunity to create a new (empty) database. Be sure your CONFIG.SYS file contains the following minimum values: FILES=20, BUFFERS=20. To find out whether your machine has a CONFIG.SYS file, issue the following commands: PROMPT $P$G [press return]. You may already be using this prompt string, but if not, at least from here on out you will know what drive and directory you are defaulting to. C: [press return...we want to log onto the C: drive] CD\ [press return], this should put us in the root directory a 'C:\>' prompt should appear. If so, type the following command: DIR C*.SYS [press return] If you do not see a file named CONFIG.SYS in the newly displayed text, you can safely assume that one does not exist. To Create CONFIG.SYS: Issue the following commands at C:\> prompt (to be a bit more technical, while logged onto the root directory of the boot drive (typically C:) of your system): Copy Con: CONFIG.SYS [press return] FILES=20 [press return] BUFFERS=20 [press F6] You should receive a '1 file copied.' message. Reboot your computer. The CONFIG.SYS file is read only during initial boot of your system. Questions about this can be resolved by looking at your DOS manual. S Y S T E M O V E R V I E W BIBL (rhymes with nibble) is a simple to use online catalog for your personal library. Written in Turbo Pascal 6.0 and using full B-tree indexing (thanks to TurboPower's B-Tree Filer package), the system is fast, small, and very efficient. Menu-driven, BIBL can be used to track your book collection, article reprints, index your vertical file, manage a small office library, and so on... In most areas bounce-bar menus are used. To select a particular option, move the bar via the cursor until your desired operation is highlighted, then press RETURN. If you're a touch typist, you might prefer pressing the highlighted letter within (or just to the left of) the choice you wish to make (e.g., Press S to activate SEARCH on the main menu). On single line menus (e.g., when displaying matches), you may hit the highlighted letter to execute the command, or move between them via the TAB key. Clicking a mouse on your menu choice will also activate it. Command Line Switches (DatabaseName /p /m /v /d) DATABASE SELECTION. Put the name (DAT extension unnecessary) of the database you want to use on the command line if desired. This will bypass the selection menu if you have more than one *.DAT/*.IX combination in the same subdirectory. For example: BIBL DEMO /m [RETURN] at the DOS prompt would activate BIBL in monochrome mode and open the database named DEMO. If on a monochrome monitor you find you can not clearly read the various BIBL status line displays, activate program with an '/m' switch (for mono), e.g., BIBL /M <cr>. OPAC (Online Public Access Catalog) . If you want to have others use your BIBL database but don't want them adding, deleting, or editing records, begin BIBL with the /p switch. This activates OPAC mode, disabling the Add function and Maintenance Menu. You may use any combination of command line arguments, in any order--with the exception that FILENAME if it appears must be the first one. [Registered version] BIBL will also run in 43 or 50 line mode (EGA or VGA) if you start the program with a /v switch. BIBL will automatically detect hardware and make the appropriate setting. Upon exit, the 25 line mode will be restored. If you use WordPerfect 5.1 as your installed editor/viewer, and are BIBL in the 43/50 line mode, your call to WordPerfect will start that package into 43/50 line mode as well. /d = doorway. If you run BIBL on a bulletin board under the DOORWAY package, using the /d switch will turn off the MAINTENANCE menu option on the main menu but still allow users to add, edit or delete records. OPENING MENU When you type BIBL at the DOS prompt, several things happen... 1) the program allocates RAM for in-memory storage of the indexes. The SHAREWARE version sets aside 40K, the REGISTERED version uses 40% of available RAM (or 40K RAM and 1/3 of EMS). 2) if you are using the SHAREWARE version, a reminder to register screen appears (actually appears about 50% of the time). 3) the program next checks your disk to see how many *.DAT files can be found... a) One, BIBL opens that database. b) More than one, a pick-list appears. Select the file you want to use by moving the light bar with the cursor arrows until desired file is highlighted--then press RETURN (or double-click mouse on desired file). 4) the main menu appears. Main Menu Options L List items in the database. This option allows you to move through the database a record at a time. The records appear in the order in which they were entered into the system. Pressing L on the main menu takes you to the last record in the file (the assumption being that you are probably more interested in the more recent records). You may move about the file via the J (Jump) command--which 'jumps' you to the record number you enter. A Add an item to the file. Use for entering data into a database. Disabled with /p switch used at startup. S Search a database. Supports a variety of search types. E Export data. Enables user to produce a variety of reports, including bibliographies. V View ASCII file(s). Allows user to look at an ASCII file. If you are using the registered version, and have installed a word processing program (e.g., WordPerfect) as your external editor/viewer, then pressing V calls that program and passes the name of the file to view. M Maintenance functions. This function provides a variety of support operations (rebuilding indexes, creating new databases, deleting databases, Shell to DOS, backup, etc.). Disabled if /p (read-only) or /d (doorway) switches are used at startup (e.g., BIBL /p [return]). D Database selection. Once you have created a second database, this function allows you to move between database files. I Information on BIBL. Pressing I on the Main Menu causes the file BIBL.HLP to display in a window on your screen. To create your own help file, make an ASCII file and name it BIBL.HLP. You do not have to worry about page breaks or other formatting. Q Quit to DOS. Closes all files, halts program and exits. DATABASES BIBL can manage an unlimited number of databases (any combination of a *.DAT and *.IX file is considered a database). While the structure of each database is the same, you may have several--enabling you to separate out records that belong together. You can create new (empty) databases from the Maintenance sub-menu. Once created, you may select (that is, make it the active database) a particular database via the Database Selection option on the main menu. The entire program operates on only 1 active database at a time. I. ADDING RECORDS TO A DATABASE Each database is limited to 2 billion records although you'll run out of disk space long before that becomes an issue. To begin working toward that 2 billion, press A as the main menu displays. A blank record appears on the screen. Enter data in the highlighted fields. If you want to skip a field, just press RETURN when the cursor is inside that field's highlighted box. When you are finished, either press return when the highlighted box is in line 10 of the note field, or press ESC. BIBL will then offer a prompt line at the bottom of the screen, asking to file the record, continue editing, verify keywords or abandon it. You may click the appropriate response with your mouse or enter the highlighted first letter of the option you desire (e.g., A to Abandon). [Y] Yes, file record. This will add the record to the database and update the index file (unless all fields in the record are empty, in which case the command to file is ignored). [N] No, edit Record. Returns cursor to 1st field of record. [ALT-V] Verify. BIBL checks the subject and each keyword against the database's index, showing you which ones are currently used. This helps with maintaining a 'controlled vocabularly.' [A] Abandon. Releases all the data you've entered for a given record and returns you to the main menu. BIBL INDEXING Five indexes are maintained in the single file: 1) the first 20 characters of the author field, 25 characters of the TITLE field, the entire SUBJECT field, each word (something with a space before and after it) of the keyword field (must be more than a single character), and a fifth index used to create temporary sorts (by call number, author/title, etc.). By putting all five indexes in a single file, performance is improved over systems that put each index in its own file--DOS does not allocate a large number of file handles for BIBL's use. Information is stored in upper case in the index file and your query is converted to upper case before a search begins--thus you don't have to worry about capitalization (although the way you enter data is the way it will display and appear in any ASCII file created by BIBL. FIELDS (Subject vs Keyword) Most fields are obvious, but you might not be familiar with the distinction we're making between subject and keyword. Put the most important term in the subject field and other less useful but desired descriptive terms in the "Keys:" field. Note that BIBL will produce reports sorted by Subject. EVERY word (anything between spaces) in the keyword field is individually indexed. Caution: No term in the keyword field can be longer than 20 characters (or it will be truncated to 20 characters in the index). The indexing algorithm considers a word to be anything between two blank spaces. If you have a compound term, include a '-' between the words so they'll be considered a single term (e.g., 'World-War-II' is considered 1 term while 'World War II' is three.). Up to 9 words in any one Keys: field will be indexed. A single letter WILL NOT be indexed. LOCATION: You may use the location field for either a classification number (if your organization system is that evolved) or simply where you have stored the physical item referenced in the BIBL record. II. SEARCHING THE DATABASE To search, press S at the main menu, then via the light bar select which field you wish to search (Author, Title, Subject, etc.). Once you have selected the field you wish to search, a 'QUERY' box will appear. Enter the text you wish to locate in this box, at the 'Query >>' prompt. You may search text in ANY field of a BIBL record. Matches are made using your input as a stem; that is, if you enter SMI and SMITH exists, you'll get a match (it's called implied truncation). Note that while retrieval on indexed fields is very fast, searching non-indexed fields (e.g., line 3 of the note field) is slower. You may abort a non-indexed search by pressing any key to interrupt. On searches, BIBL first reads through the database collecting matching records, then shows them (e.g., Match 1 of 50). BIBL will collect only the first 650 matches. If you have more than 650 matches, you will receive a message noting that the match limit was exceeded. You should narrow your search. On indexed field searches, if BIBL can not find a match for your query, it will display several index entries that come before and after where your query would have fallen in the index. As your database grows, this becomes more useful. If you want to abandon searching after you have selected a particular field to search, press RETURN instead of entering a search statement at the 'Query >>' prompt. You will be returned to the main menu. BOOLEAN SEARCHING (AND / OR / NOT) Use BOOLEAN search to search for up to 4 terms in a record. You may search either the full record or limit the search to the keyword field. When the full record is searched, a high speed search algorithm (Boyer-Moore) is employed--this yields a significant performance improvement over searching just the keyword field--where BIBL uses a more traditional approach (reading each record and comparing the field to your input). Registered version supports dumping the results of a boolean search to disk. You may select either BIX format (for subsequent transfer to another datbase) or plain ASCII (no labels, formatted like QUERY.TXT entries). You give BIBL a name for the output file and based on your format choice, the extension (BIX or TXT) is automatically appended. LAN users: If you have directed BIBL to look on a remote drive for the database (via BIBLPATH.CFG), the BIX file will be put where BIBL.EXE resides, not where the database (*.DAT and *.IX file) resides. III. EDITING/DELETING RECORDS IN THE DATABASE You may enter EDIT mode either via a search or by the LIST function (press E when the desired record displays). As you first enter EDIT mode, the author's name field will be highlighted. Make any changes you desire. See Appendix C for editing keystrokes that are supported by BIBL's editor. When you have finished making changes, press ESC. If you've made changes, you'll be prompted as to whether you want to replace the record in the database with this new version. Y - The index will be updated if changes were made. N - Changes will be discarded. Original redisplays. You may also enter EDIT mode via the 'List records in the database' option from the main menu. The only difference between editing from this menu choice instead of SEARCH is that BIBL will display all records in the database, beginning with the last record. IV. SYSTEM MAINTENANCE The MAINTENANCE function offers several options: - Convert Shareware to REGISTERED. - Rebuild Indexes - Call External Editor/Call Up Any ASCII files - Shell to DOS - Install Editor/Viewer - UnInstall Editor/Viewer - Make a new database - Delete a database - ASCII Import (Read BIX files) - Global Change - Backup database (create archive) - Total Value field for database A. CONVERT SHAREWARE to REGISTERED. With Release 5.25 we've introduced a new wrinkle, which should prove popular with registered users. Instead of having to obtain a new copy of BIBL with the registered features, you can instantly upgrade the shareware version and 'unlock' the registered features. Here's how it works: When you register, you will receive by return mail a registration number. Select option C under the Maintenance sub-menu, then enter the number EXACTLY as it appears. BIBL will verify that it is a valid number (we do some check-digit math in case you're interested in such things) and will then create an ASCII file (BIBL.REG) which stores that number. From then on, when BIBL activates from the DOS prompt, it will read that file, verify the number, and present you the user with a registered version of the program. The real value is that forever more you can upgrade any SHAREWARE release to REGISTERED, just by entering your secret number. Actually, as long as you leave BIBL.REG in your BIBL sub-directory, the upgrade process will be automatic. You won't have to check our BBS for the latest registered version or have to send us a disk or pay the extra $ 5.00 to receive one by return mail. If you see a newer shareware version on a BBS or CompuServe, download it and immediately have the benefits of an upgraded registered version. B. REBUILDING INDEXES BIBL includes an index rebuild function to create new indexes from the database file on demand. You may never need this function but if you have to rebuild your file using BRX (which does not do a complete job of indexing your file ), or wish to physically purge deleted records from your file, this option will perform the task. C. CALL EXTERNAL EDITOR/CALL UP ASCII FILE You may view your savefile (QUERY.TXT) or any other ASCII file from within BIBL. The viewer built into BIBL is quite powerful but limited to files that are no larger than the amount of RAM available after BIBL loads. It responds to a mouse with the following options: Click on small box in upper left.....close window Click on scroll bars............move through file Click on [arrow] in upper right corner.......Zoom Click on top line of window....move window screen Click on lower right corner, drag..........resize Keyboard commands: F5 Toggle Zoom ALT-F5 Resize toggle CTRL-F5 Move the window. CTRL PgUp/PgDn Top/Bottom of file ESC or F10 Close window External viewer. If you have an external program linked to BIBL, that program is called and passed the name of the file you want to view. D. SHELL TO DOS BIBL allows you to drop out of the program momentarily and return to your DOS prompt. This option allows you to delete files, use a program like LIST to view a file, check disk space, or do other DOS-type things. All but 140K of your RAM is returned to the system for the DOS prompt. When you type EXIT, BIBL will reactivate and check to see that the operating system is still defaulting to the sub-directory where your BIBL files are kept. If not, BIBL will change to that drive and directory before continuing. If BIBL is unable to change to the original sub-directory, you will receive a message to that effect...so you can manually issue the command (e.g., CD\BIBL <cr>) from the DOS prompt. E. INSTALL EDITOR/VIEWER BIBL allows you to specify some program other than BIBL to handle viewing of your save file or other text files as well as editing and printing of reports. The program you use must be capable of accepting an ASCII file as a command line argument (e.g., WP filename <cr>). BIBL will send the name of your external program (drive, path, program name and extension) to DOS as well as the name of the file (drive, path, filename, and extension). This allows you to access an external program on another drive if desired. BIBL creates a simple configuration file (BIBL.CFG) when an external viewer/editor is defined. If you want to remove the editor/viewer altogether, just delete the BIBL.CFG file. If you later install another package, BIBL will create the configuration file again. Note: UNinstall Editor will accomplish this deletion for you. BIBL swaps most of itself out to disk (or EMS if available), freeing up more system memory for your editor/viewer. EMS will be automatically used if available, otherwise the swap is to disk. While the program normally requires 460K or more to run, after compressing itself and swapping out, a 55-65K kernel of BIBL remains in memory--enabling you to use a very large program (e.g., WordPerfect) as your editor/viewer. When the external program finishes, BIBL returns! If BIBL encounters a problem (too little memory, invalid name for the viewer/editor program, viewer/editor not found in path, etc.), it will just ignore the request and return to the main menu. Once installed, the name of the viewing program (no extension) appears on the BIBL main menu in the VIEW option bar. F. MAKE A NEW DATABASE. To create a new, empty database, press M on the maintenance menu, then enter a name for the database file. You may enter up to 8 letters for your database name. You should try to give the file a name that will later give some indication of the file's contents. TIP: When creating databases, give your most popular file a name that sorts first. The Database Selection option on the main menu sorts the various *.DAT files before displaying them. The first file in the list will be highlighted when the list displays. If it is the file you want, just press RETURN (or ESC). Note that you can also specify a database on the command line when activating BIBL from the DOS prompt (e.g., BIBL Myfile). G. DELETE A DATABASE. You may use this function to delete a database and it's associated index file. You may also delete a database and index simple using the DOS delete command while at the DOS prompt. BIBL dynamically determines your databases by scanning the directory where BIBL.EXE resides for files ending with the *.DAT extension. You may NOT DELETE the database you are currently using. You should not use the DAT extension for any export files you create, nor should you have any file with a DAT extension (that's not a BIBL database) in your BIBL subdirectory...if you do, BIBL will assume it's a database and present the file as a valid choice. H. ASCII Import Using the ASCII import option enables you to read any labelled ASCII file into the currently active BIBL database. The file separated with **'s and each line is labelled. The labelled option under the Export Menu creates this format as does the Transfer option when displaying an individual record. If you want to experiment with ASCII import (say you're trying to import an ASCII file from some other source--like bibliographic data downloaded from a CD-ROM), you should follow these steps: 1. Use MAKE A NEW DATABASE option on maintenance menu to create a database called something like TEST 2. Use DATABASE SELECTION on the main menu to select the TEST database. 3. Run ASCII import from the maintenance menu. You BIX file must be in the same subdirectory where BIBL.EXE resides. 4. After reviewing the results (the records added to TEST), select the database you want to use and run ASCII import again. When finished, you can delete TEST.DAT and TEST.IX via Delete a Database (on the maintenance submenu). For downloads from ERIC, ABI/Inform, PsycInfo, Medline and/or NOTIS get MAKEBIX...from the GMUtant BBS or Compuserve (IBM APPS). I. GLOBAL CHANGE You may make global changes ('find & replace') to text in any record across your database. The unregistered version is limited to making these global changes on the Subject and/or location fields. The registered version of BIBL allows you to change the text in any field of all records for a given database. To make a global find and replacement, select the field you want to modify (the database will be the currently active file--the database that displays on the status bar at the bottom of your screen). After selecting the field to modify, you must next enter the original text (what's currently in the record(s)) and then the new text. You may instruct BIBL to ignore case when attempting to match or to consider a match valid only when the case is the same. TIP: Be advised that the subsitution you instruct BIBL to make will occur anywhere BIBL finds a match for your 'change' text. Without a bit of thought on your part, this can quickly become a nightmare. If you elect to change a short word--one that also appears as part of a larger word in the same field--you can have problems. For example, asking BIBL to change NETWORK to LAN can (if you also have NETWORKING in the same field) lead rather quickly to LANING... V. OUTPUT OPTIONS / REPORTS / BIBLIOGRAPHIES While BIBL offers only limited print support, it will dump your database to disk in an ASCII file--which you can then edit and print using your favorite word processor. Where you are given the option of naming the file, you should use a *.TXT extension when possible. This will allow you to see all available export files under the CALL EXTERNAL EDITOR function which has a *.TXT mask. Content Name BIBL will give ASCII file Author AUTHLIST.TXT (author/title sort) Title TITLLIST.TXT Subject SUBJLIST.TXT Delimited BIBLDLM.TXT Labelled BIBLLIST.BIX You may assign names to these files...and include a pathname if desired. For example, to put the file on a floppy, preceed the name with A: (e.g.,A:MYFILE.TXT). Bibliographies User names this file. Registered version also offers option of using SOFT RETURNS. Keyword List KEYWORD.TXT (user can rename) Title List TIBRIEF.TXT Subject List SUBRIEF.TXT Author List AUBRIEF.TXT A/T/L (Author/Title/Location) ATLLIST.TXT L/A/T (Location/Author/Title) LATLIST.TXT User-Defined User names this BIBL can create ASCII files (full, annotated or brief form) for all records that contain your search string. The registered version also supports LABELLED output of bibliographies. Using this feature and the ASCII Import option on the Maintenance menu, you can select out records from one database based on text that appears in a given field, then use ASCII Import to read those records into another database. This gives you an 'automatic' means of moving records from one database to another. Registered version supports bibliography creation on ANY field in the record. The registered version of BIBL also provides the option to create output files using soft returns instead of hard ASCII returns) after each line. This greatly simplifies subsequent editing if using a word processor that supports scalable fonts. Annotated form will produce a listing with author, title, publisher and the notes fields. Brief includes only the author, title and publisher field. You assign the name for the bibliography output file. If the name is already in use, BIBL asks you to use another name. Note that using the Word Processing [WP] format option will produce a citation where fields follow one another on a line. A hard return follows the PUBL field. Smart Punctuation. As BIBL creates your bibliography, it will check to see if each field ends with punctuation. If so, the existing punctuation will be written to your file. If not, BIBL will add periods after each field. This saves you having to use end-of-field punctuation in your BIBL database entry. DELIMITED FORMAT Delimited format is used when you want to move your BIBL database to dBASE or some other database system (why?). The next few paragraphs point out a few things you should be aware of: Note that in delimited format BIBL will change any quotation mark that appears in the Title, Keyword or Note fields to a single quote--to preserve the exported data's integrity. If any double quotes were to appear in the exported data (that is, anywhere other than between the fields), the importing program might not process the data correctly. For example, if you have: Jones is author of the article, "This is My Life's Work." in your note field, under delimited format, BIBL will export: "Jones is author of the article, 'This is My Life's Work.'" A CR/LF appears at the end of each record. dBASE will accept this for input if you first set up a dBASE file with the proper structure. Multi-line fields (e.g., author, title, publisher and note) are combined into single comma-quote delimited strings. You can calculate the maximum length by consulting the record format at the end of this documentation (for example, a author field can be up to 140 characters long -- since it is composed of two 70 character lines). LIST SUBJECTS/LIST KEYWORDS You should use these export functions periodically to check the uniformity of your subject headings and descriptor fields. For example, if your list shows you have 10 items under computer and 1 under computers, you should edit the COMPUTERS entry (changing it to COMPUTER). As an aid in helping you identify the records, a bit of the title is included with each entry. Note that there is an entry in the list for each heading in a record (if you have 10 records with the subject BASEBALL, you'll get 10 entries for BASEBALL in the SUBRIEF.TXT file). KEYWORD.TXT - this option lists all terms used in the keyword field of your database. With each term, the number of times it appears is also listed. This list can be a big help in eliminating redundant terms and consolidating similar terms to yield a stronger database. Related Topics Send To Disk. Beyond creating large reports, during any search you may elect to send a copy of a single record to an ASCII file (QUERY.TXT). Each time you press 'S' a copy is appended to this file. When you are finished with the file, delete it (via DOS) or rename it. Then when you next send a record to disk, BIBL will create a new copy of QUERY.TXT. Transfer: Any time an individual record is displayed, you have the option of copying it to a transfer file (TRANSFER.BIX). Pressing T (or clicking on the word 'Transfer' will add the record to TRANSFER.BIX. To move the records in TRANSFER.BIX use ASCII import on the maintenance menu. Be sure to delete any existing TRANSFER.BIX file if you want to make a file of new records...if TRANSFER.BIX exists on your disk, transferred records will be appended to it. If it is missing when 'T' is pressed, BIBL will create a new copy of it. Registered users can also transfer records in groups, based on text occurring in any field. Select Bibliographies/Transfer on the Export menu, then proceed as you would when creating a bibliography. When prompted for output format, select Labelled. You will next be asked if you want to delete transferred records from your original file. You may want to run this option once before you go back and ask BIBL to delete copied records (just to verify that you did retrieve the records you wanted AND to insure that you were able to import them to another database successfully). IMPORTANT Once you ask BIBL to delete these records, they will be gone...deleted from the original database which will then be packed and re-indexed before returning to the Main Menu! USAGE NOTES / TIPS A. Here are some of the ways we've heard BIBL is used: - as an online index to a personal book collection. - tracking magazine articles. - a videotape collection for a large university is cataloged using BIBL/NET. The network version of BIBL is used so that simultaneous access is provided even as the library staff add records. - indexing a vertical file (for non-library types, a vertical file is usually a filing cabinet of clippings, brochures, etc.). - using BIBL instead of 3x5 cards for research. - tracking reserve reading materials in a corporate library. - with /p (OPAC) switch set, running BIBL as a DOOR on a BBS to provide users an online catalog. - Managing an office library. - A computer center uses BIBL to track documentation - A public service agency has 50+ copies of BIBL. The home office creates databases and sends them out to branches. With OPAC mode set, the integrity of the files is preserved. B. Using WordPefect (5.0 or 5.1) as your external editor (or viewer or printer) with BIBL While BIBL does not possess a direct interface to WordPerfect it does work particularly well with version 5.1 of that software. Follow the sequence below to install WordPerfect as your editor/viewer: Note: the sequence is the same for any word-processor...just be sure that the program accepts a filename to edit on the command line (e.g., WP MYFILE [RETURN] on the DOS command line will start WordPerfect and load a file named MYFILE). WordStar also behaves this way as do other programs. 1. Select MAINTENANCE from the BIBL main menu (press M) 2. Press I (Install Editor/Viewer). 3. Enter the full path name to your copy of WP.EXE (e.g., C:\WP51\WP.EXE). Now, when you select CALL UP ASCII FILE under the MAINTENANCE option, BIBL will load WordPerfect and pass along the name of the file you want to view, edit or print. When you are finished with the document, press F7 to save and then exit WordPerfect...you will be returned to BIBL. The file you worked on is stored on the drive and sub-directory where BIBL.EXE resides. C. Remote Drives / LAN usage (registered version only). You may store your database and index files on a drive/sub-directory other than were the BIBL.EXE file is kept. This will allow you to use BIBL on a LAN or in an environment where disk drives are shared between users. While this version of BIBL is a single user product (BIBL/NET is also available) you can store your database and index on the server disk. IMPORTANT: BIBL databases MUST reside in a subdirectory, not the root directory, of any remote drive you use. For example, say you want to put a BIBL database and index (*.DAT and *.IX) file on a RAM disk. Be sure to create a subdirectory on your RAM drive and move the files there. Do not simply create a drive (e.g., D:) and copy the files there. If you try to run BIBL using a root directory, you'll get a error about locked databases and the system won't operate! To point BIBL to some location other than the drive/directory where BIBL.EXE resides, you must create a configuration file. Name of file: BIBLPATH.CFG Location: Must reside in same directory as BIBL.EXE Purpose: When BIBL first initializes, if it finds BIBLPATH.CFG it opens the file and reads the data path statement. That path then is added to all subsequent database access calls. Format: ASCII text file that contains the following statement: DATAPATH=X:\XXXXX where X:\XXXXX is the full path name of the subdirectory you want to use for storing the database & index file. Example: Suppose you store BIBL.EXE in your C:\BIBL subdirectory, and you want to put your datafiles and indexes on the fileserver (say, drive H:) and in a special subdirectory reserved for your use (e.g., MYFILES\BIBL). Create BIBLPATH.CFG and enter this statement: DATAPATH=H:\MYFILES\BIBL (no need for the '\' on the end of the line) To create: You can use an ASCII editor (e.g., QEDIT) or simply create the file from the DOS prompt. Here's how you create the file using only DOS: 1) Log onto the subdirectory where BIBL.EXE resides 2) At the DOS prompt, type the following lines. Use UPPER CASE. ([CR] means press RETURN. [F6] means press F6.) COPY CON: BIBLPATH.CFG[CR] DATAPATH=X:\XXXXXX[CR] [F6] D. Using BIBL's [WP] format with WordPefect. Here's how you create a WordPerfect-ready version of your database, (printing author, title and publisher fields), sorted by Author, then title: 1. Press E on the BIBL main menu (EXPORT). 2. Press M (user-selects). 3. Answer 'Y' that you want to continue. 4. Enter 123 and press return (to indicate that you want fields one (author), two (title) and three (publisher). 5. Enter 'Y' to indicate that you're satisfied with fields. 6. Enter 1 to indicate that sort should be on author (it will actually be on author, then title within author). 7. Enter 'E' to indicate that you want [WP] format. 8. Enter the name you want to give your output file. If you are using WordPerfect as your external editor, once BIBL finishes making your file and returns to the main menu, press M (for Maintenance), then press C to 'CALL External Editor, enter the name you gave the file in step 8 (or just hit return and pick from the *.TXT files displayed), then sit back as BIBL compresses itself, then loads WordPerfect (passing along the name of your file). If you need to reset your margins (because the text is wrapping around incorrectly), go to the top of the document and press SHIFT-F8, then L (for Line), then M for margins. E. Modifying HELP display (INFORMATION on the main menu). BIBL displays the file BIBL.HLP when 'I' is pressed on the Main Menu. If you want to change the help display file, just rename any ASCII file to BIBL.HLP and BIBL will display it... F. BACKUP? Many users have found that using the LABELLED option under Export provides a space-saving means of making a backup copy of your database(s). Since only the data from your database is exported (not the empty spaces inside each record), the resulting file is usually about 40% smaller than your database. With ASCII Import (on Maintenance menu), you can read this file back into BIBL should you ever need to reconstitute your database. Another backup option exists for users of PKZIP, LHA or ARJ (archive utilties). You may use BIBL to 'drive' any one of three third-party archiving utility programs (LHA.EXE - .LZH files; PKZIP.EXE - .ZIP files, and ARJ.EXE - .ARJ files). The archiving program *MUST* be either in your BIBL subdirectory or in a sub-directory that is included in your DOS path statement. If one of the supported archiving programs is not found, BIBL will ignore the request. If it is found, BIBL compresses itself in memory (down to about 91K), then launches the archiving program. When it is finished, BIBL re-expands in memory and continues running. If you have EMS memory, BIBL will swap itself to EMS during this process (otherwise, it swaps to disk). Both the data file (*.DAT) and the index file (*.IX) are combined in the archive you create. Since BIBL always initializes both records and index entries with 0's before use, these programs achieve a compression of 85 - 90%! Thus, you can probably fit a 2,000 record database (and index) on a 360K floppy. Technical Specs: 1. Memory required. BIBL requires a minimum of 456K RAM 2. Pascal Record Structure bookrec = RECORD recordstatus : longint; idnum : string[10]; {reserved for future} value : string[6]; {value/cost field} author1 : string[70]; author2 : string[70]; Title1 : string[70]; title2 : STRING[70]; title3 : string[70]; publ : STRING[70]; publ2 : string[70]; class : STRING[40]; subject1 : string[30]; subject2 : STRING[70]; {descriptor field} flag1 : char; {Used by BIBL/NET} flag2 : char; { " } flag3 : char; { " }7 createdate : string[7]; {record creation date} note1 : STRING[70]; note2 : STRING[70]; note3 : STRING[70]; note4 : STRING[70]; note5 : STRING[70]; note6 : STRING[70]; note7 : string[70]; note8 : string[70]; note9 : string[70]; note10 : string[70]; end; Indexes (the following keys are maintained in each .IX file): Author first 20 characters of field (stored upper case) Title first 25 characters of the field (stored upper case) Subject all characters of subject1 (stored upper case) Keyword first each word of the field is extracted (a word being a string of characters separated by space or comma). Up to 20 characters of each 'word' is indexed. Up to 9 words from any one line are indexed. If you have 10 words on the line, the ninth is ignored. IMPORTANT: place a '-' between words you want BIBL to index together. A fifth index is reserved for 'on-the-fly' reports (bibliographies, sort on publisher or location field, etc). Data stored in this index is compressed (to allow larger text values to be represented. The key length is 15 characters although with data compression, 20 characters are used to build the key). During bibliography production (Option D on Export Menu), the key value for this fifth index is: author (14 characters)+title (6 characters) which yields an author/title sort. During User-Defined output (Option M on Export Menu), with a sort on the location field (field #4), the sort key is location (15 characters)+author (5 characters), to yield a location/author sort. This same sort is used on 'Location first' reports. If publisher field sort is selected for Option M, then 20 characters of the publisher field are used to generate the key. File extensions used by BIBL: .DAT - a datafile .IX - the index to a DAT datafile. .HLP - Help file (displays when I is pressed on Main Menu) .SAV - temporary file, used during index rebuild/purge. .DBL - ASCII file used to store display text modifications for a particular database. The *.DAT and *.IX files together form 'a database.' You must have the same name on both you .DAT and .IX files--usually taken care of by BIBL but if you rename a database via DOS (for example, renaming DEMO.DAT to MYFILE.DAT, be sure to rename DEMO.IX to MYFILE.IX too!). If you modify the labels, this 'database' will also include a *.DBL file. .TXT - any ASCII file. .BIX - BIBL Import/Export. A labelled ASCII file. This file uses a specific format where each field is labelled (e.g., A1:, A2: for the 2 author fields, T1: T2: T3: for the title fields, and so on. Each record in the file is separated by '**'. The ASCII import function on the Maintenance Menu will read a BIX file and write the information to BIBL records. You can use this facility for backing up your database or moving records from one database to another. TIP. Many users find BIX files are great for doing massive edits across a database (assuming you have an ASCII editor or know how to save an ASCII file from within your favorite word-processor). Just export your database as a BIX file, then use your editor to make global changes across the file. When you're finished, save it back as a plain ASCII file (e.g., CTRL-F5,Text,Save in WordPerfect). Create a new database structure within BIBL to hold this new data (we don't want to import it into the same database we used to get the BIX file or we'll have duplicates). Import it into the new database via Maintenance. When you're convinced it all worked correctly, just delete the older version of the database. BIBL.EXE has been compressed with PKLITE version 1.15 Questions, comments, complaints, encouragement??? Clyde W. Grotophorst, Route 1, Box 296, Hamilton, Virginia 22068 voice: (703) 993-2239 or call the GMUtant OnLine BBS (703) 993-2219, and leave a comment for the Sysop. You may also reach the author via Compuserve (70404,3376), or via the internet (wallyg@fen1.gmu.edu). Appendix A Modifying field display text Beginning with release 7.1, it is possible to modify the way BIBL refers to certain fields in a particular database. Note: this functionality is restricted to modifying the LOCATION field in the SHAREWARE version. A BIBL record defaults to the following field labels (not all the note field is shown for brevity sake): Auth: : Title: : : Publ: : Locn: Date: Subj: Value: Desc: Note: : It is possible to modify these labels on the record display screen, the data entry screen and the edit screen. To do so, you must create an ASCII file similar to the one shown below. In the sample below, we want to modify the Location field (uses the label Locn: in the above example) to show Class: (as in classification). First, with an ASCII editor create a file with the same filename as the database you want to perform this modification on...but give the file a DBL extension. For example, say you wanted to modify the DEMO.DAT database that comes with BIBL, you'd create a file named DEMO.DBL Using the convention established with BIX files (where each field is labelled), you'd enter the following line in the file: CL=Class: CLMENU=Call Nmbr The CL= line governs what label BIBL will use for that field when displaying a record. The CLMENU= line governs how BIBL will refer to the field on the SEARCH and EXPORT menu screens. Limitations: The label text can be no more than 6 characters. The menu text can not exceed 9 characters. Any field you do not modify in your *.DBL file will retain the BIBL default value. Here's a complete sample file for a database that's being used not as a book catalog but as a faculty directory: A1= Name: A2=Phone: T1=Membr: PB= Dept: P2= Schl: CL= Rank: SU=Rsrch: DE= Desc: N1= Note: VL= Cost: AUMENU=Professor TIMENU=Membrship PBMENU=Affiliate SUMENU=Research CLMENU=Rank With these 13 lines (and yes, each entry must occupy a single line and begin in the first position of the left margin), we change the look of this one database...all other BIBL databases (unless they too have a corresponding DBL file) will use the BIBL book-oriented defaults. Any BIBL field label can be modified. Five fields may be renamed throughout the program: Author, Title, Publisher, Location and Subject. When you delete a database that has an associated DBL file, BIBL will ask if you want that label file removed as well. Leaving it causes no problems other than consuming a few hundred bytes of disk space. You may use WordPerfect to create a label configuration file but be sure to save the file using CTRL-F5 (text out). If you want a database to revert to the original default labels and field names, just delete the associated *.DBL file for that database. ** IMPORTANT ** The operation of the program is not changed by these modifications.If, for example, you do as we've shown in the sample above and divide the author field into 2 fields (one for name and one for phone), BIBL will still treat them as an entity when producing reports -- which in this case would concatenate (or join) them. Finally, when assigning values to AUMENU, TIMENU, CLMENU and SUMENU, be sure that you *DO NOT* have the same letter beginning more than one values--or use the same first letter as is used by one of the fields that you can not change (e.g., D for Descriptor). In several instances during operation, BIBL will accept the initial letter of the strings you assign as the hot key. If two begin with the same letter, pressing that letter will always activate the first term (for example, don't have AUMENU=Editor and SUMENU=Edition -- both begin with an E). Appendix B. Value field Beginning with release 7.4, BIBL will now track a value for each item in a database. Many users have requested this field (to help with insurance valuations of their collections). The value field is limited to 6 spaces (so you can store between 0 - 999.99 for a given item). Should you have an item worth more than 999.99 you can omit the decimal and track values up to 999999. When BIBL computes the total value for a database, it will treat 999999 as 999999.00. The value field label may be changed (using VL= in the *.DBL file). Value appears only in the BIX file (label VL=) or under the USER- SELECTS option under export. It can be read into a BIBL record when using ASCII import. Do not include a $ in your value for an item (e.g., don't enter $ 5.00 -- use 5.00 instead). BIBL will replace any $'s found with 0's. Appendix C. Editing keystrokes supported (use during ADD and/or EDIT): If you know WordStar (or use one of the Borland editors), you'll find most of BIBL's edit commands perform as you'd expect (^ = Control key): ^F or CTRL -> word right ^S - character left ^A or CTRL <- word left ^D - character right ^T - delete word right ^Y - delete line ^E - up one line ^X - down a line ^H - backspace If you're using a mouse, you can click on a field to highlight it for subsequent editing. ================================================================== BIBL shows significant performance gains when used with a disk caching software package. At a minimum, if you're using DOS 5 (good), activate SMARTDRIVE. If you have DR DOS 6 (better), use PCKWIK. There are many other disk caching packages available from various software vendors. As with any disk-intensive application, a defragmented disk is also a plus... =================================================================